Don't re-run setup too quickly.
After the IO Libraries Setup program exits, it takes several seconds to clean up and unload itself from memory. If Setup is re-run before this process is complete, you may see an error message or find that the re-installation does not behave as expected.
Be sure to wait until the 'InstallShield Wizard' box on the Windows task bar has disappeared before attempting to re-run the IO Libraries Setup.
Installing on dual boot systems can cause problems.
Installing the IO Libraries on dual boot systems that share a common 'Program Files' directory between two operating systems is not recommended and may cause problems.
- If the IO Libraries are installed in the same directory for both operating systems (e.g. 'Program Files\Agilent\IO Libraries'), files for one OS may overwrite files for the other OS.
- InstallShield uses a directory under 'Program Files' to log the name and location of files for later un-installation as well as the components that are currently installed. Uninstalling or modifying an installation on one OS may affect the files for the other OS rather that the currently booted OS, even if these files are installed in different directories.
The syntax for specifying an option with self-installing .exe file 'iolibs.exe' is different from specifying a parameter with Setup.exe on the CD.
To specify options to Setup, invoke Setup from a command prompt and separate the options with spaces:
e.g. 'setup auto novisa'
When installing from the self-installing .exe file, you must include a '-a' option as the first option:
e.g. 'iolibs -a auto novisa'
Setup from the self-installing .exe file may prompt for bogus disk.
If you install the IO Libraries from the self-installing .exe file using a parameter (e.g. 'iolibs -a auto'), you may be prompted to insert a non-existent disk. You may continue the installation by specifying the last available disk in the set.
After installation on Windows 95 and Windows 98, Windows may fail to boot.
When adding paths to the PATH statement in Autoexec.bat, InstallShield does not recognize '@PATH' as a path statement. It will create a second 'SET PATH' statement. If there is a second PATH statement, it will replace the existing Windows PATH and end up removing the Windows directories from the PATH.
If Windows fails to boot with a message 'Cannot find WIN.COM, unable to continue loading Windows', you will need to edit the additional PATH statement in Autoexec.bat so the Windows directories are again included in the PATH.
- From the DOS prompt type 'c:\windows\command\edit c:\autoexec.bat'. (Substitute the actual paths if you have a non-standard installation.)
- Find the last 'SET PATH=...' statement and insert '%path%;' immediately after the equals sign. (e.g. 'SET PATH=%path%;...' and don't forget the semi-colon separator.)
- Save the modified file and reboot. Windows should now boot normally.
Electronic Manuals won't run from the Agilent IO Libraries Control.
You need to have Adobe Acrobat installed to view the electronic IO Libraries manuals.
- If you select a manual from the 'Program | Agilent IO Libraries' menu, you will see an 'Open With' dialog box.
- If you select a manual from the 'Agilent IO Libraries Control | View Documentation' menu, nothing will happen.
You can install Adobe Acrobat from the 'Adobe' directory on the IO Libraries CD or you can download it from http://www.adobe.com.
⌐ Copyright 1995-2000 Agilent Technologies. All Rights Reserved.